fix(dev-infra): do not run the lock-closed GitHub action on forks
#36000
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, the `lock-closed` GitHub action, which runs daily and locks closed inactive issues, was run on each fork of the `angular/angular` repo. While the action is a [no-op on forks][1], it make still fail from time to time, generating a confusing notification e-mail for the fork owner. This commit configures the `lock-closed` action to only run on the main `angular/angular` repository (using the method suggested [here][2]). [1]: https://github.com/angular/dev-infra/blob/13b25d383/github-actions/lock-closed/src/main.ts#L117 [2]: https://github.community/t5/GitHub-Actions/Do-not-run-cron-workflows-in-forks/td-p/46756
gkalpak
added
area: dev-infra
josephperrott
removed
the
action: review
matsko
pushed a commit
that referenced
this pull request
Mar 11, 2020
…36000) Previously, the `lock-closed` GitHub action, which runs daily and locks closed inactive issues, was run on each fork of the `angular/angular` repo. While the action is a [no-op on forks][1], it make still fail from time to time, generating a confusing notification e-mail for the fork owner. This commit configures the `lock-closed` action to only run on the main `angular/angular` repository (using the method suggested [here][2]). [1]: https://github.com/angular/dev-infra/blob/13b25d383/github-actions/lock-closed/src/main.ts#L117 [2]: https://github.community/t5/GitHub-Actions/Do-not-run-cron-workflows-in-forks/td-p/46756 PR Close #36000
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the
lock-closedGitHub action, which runs daily and locks closed inactive issues, was run on each fork of theangular/angularrepo. While the action is a no-op on forks, it make still fail from time to time, generating a confusing notification e-mail for the fork owner.This commit configures the
lock-closedaction to only run on the mainangular/angularrepository (using the method suggested here).